home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d21
/
qemm1289.arc
/
QEMM1211.MSG
< prev
next >
Wrap
Internet Message Format
|
1989-12-18
|
11KB
From: Allan Nelson Area: DESQview
To: Peter Stern 08 Dec 89 16:55:44
Subject: Re: Qemm 386 Problems... Rec'd
Re your problems with Telix, I might suggest upgrading to v3.12 which is just
out. It claims to be DV aware. As for 9600 baud problems,I haven't had any
yet using the HST and Telix.
Allan
--- Lynx II
* Origin: The Fireside, Houston, Texas (1:106/114)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: Miles Simmons Area: DESQview
To: Everyone 07 Dec 89 18:14:00
Subject: DV & QBASIC & Two Monitor
I am using DV with Qemm on a 386/20. I am running QBASIC on both monitors
throw dos and find that the programs are VERY slow. I can watch the screens
being drawn and it takes about 2.5 minutes to run a program which normally
takes about 23 seconds. I have tried tuning the performance from 1 to 1
.....5 to 12 and everything in between. Any help will be appreciated!
--- via Quickpoint XRS 3.0
* Origin: *** If it ain't GOOD.....then it ain't ME !*** (Quick 1:231/20.7)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: Mike Embry Area: DESQview
To: Peter Stern 07 Dec 89 21:10:00
Subject: Re: QEMM 386 problems... Rec'd
ME> 1) Whenever I use use Telix at 9600 baud it will lock
ME> up sooner or later. This seems to only happen with
ME> BBSs that are 1t 9600 baud+.
PS> Same trouble here. Telix has been unreliable under Desqview with PS>
random lock ups. The only way I have found to gain some measure of PS>
reliability is to load Tame203 before Telix. It's not perfect but PS> it
works.
Thanks for the reply, I'll give Tame203 a try. Telix ran fine under DESQview
286 but I've heard that Telix is a keyboard polling hog. I can see where
that might be a real problem at 19,200. Allegedly the next version of Telix
was suppossed to be DESQview aware but I don't know if it's out yet.
Mike
--- QuickBBS v2.04
* Origin: The Exterminator BBS Node-1 HST/DS 1200-38400(602)842-4635
(1:114/33)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: George Heymann Of 307/7 Area: DESQview
To: All 07 Dec 89 19:43:30
Subject: Screen Glitching
I am having trouble with VGA graphics screens glitching within Desqview. When
I say glitching I mean that odd pixels don't get initialized properly or are
turned on to the wrong color. I am using Desqview 386 with the QEMM memmory
manager. My Video card is a Packard Bell VGA card that uses the Paradise VGA
Chip Set and is 100% register compatible with the IBM VGA standard, although
the card has some extended resolutions modes in addition to the standard modes.
The only way I've found to get around the screen glitching problems is to go
into Desqviews setup program and select "Other" as my video setup with no
video driver. This takes care of the glitching problem but creates a second
one. That is all VGA screens must be run full screen. It will not allow me to
Virtualize Graphics screens without a driver. I tried, this on several VGA
cards including, the Compaq VGA card, one from Everex, a standard Paradise
VGA+ and my Packard Bell VGA card with the same results.
Anyone have any suggestions, I have tried getting a solution directly from
Quarterdeck but they take an average of 6 weeks to reply to my questions, by
the time they get back to me with a suggestion, "That doesn't work", then its
6 more weeks, waiting time.......For having a great product which I feel
Desqview is !!!!, <<<<THEIR SERVICE SURE COULD BE ALLOT BETTER>>>>
--- FIDOdoor/ST 1.4c
* Origin: TTDP, Home of the FIDOdoor Programs (719)-543-1869<-HST (1:307/7.0)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: Ed Zell Area: DESQview
To: All 07 Dec 89 21:01:16
Subject: DV with MainFrame Software
I was just curious if anyone has any experience using DV (2.25) on
a 386 system that is attached to an IBM mainframe via coax?
We are running a Micronics 386 system with an IBM 3278 emulator card.
The mainframe software is called VMBOND and it allows you to hot key
(with alt-ESC) to a 3278 mod 2 session. Once you do that, the PC
side is frozen until you return to it. This forces us to load the
3278 software before DV 'cause it locks up in a window. The 3278
emulation software also provides virtual PC disks which reside on
the mainframe as CMS files.
Anyway, our main problem is that the system will lock up when hot keying
to the mainframe if DV is active and QEMM present. Remove QEMM and
the problem goes away, but so does access to 3+ meg of memory and
most of DV's functionality.
The second problem is that certain VMBOND utilities that manipulate
the virtual drives do not work correctly. I have traced it down to
a device driver IOCTL call that returns an error under DV but works
under straight DOS.
I would appreciate any suggestions and would be willing to make the
long distance call if there is too much for an echo message. Thanks
in advance.
--- D'Bridge 1.21
* Origin: EZ_Down_on_the_Farm (1:232/17.3)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: Martins Gulbis Area: DESQview
To: All 06 Dec 89 03:48:50
Subject: Problem with Virt. Text/Graphics
I posted this question about 2-3 weeks ago and got a couple
of responses, telling me I should use 'EXCLUDE=C000-C7FF' for
QEMM in my config.sys file. I have done that but I still have the
same problem. In hoping that someone may have a solution I am
repeating the question:
I have just recently purchased a 386SX machine with 2MB memory
and an AMI bios. I installed both qemm386 and DesqView. At first,
it seemed that I couldn't get some things to work. For example, the 128k dos
window that is automatically installed worked, but the
'Big Dos' window would hang the system. I would be able to press
one or two keys and then the system would be locked up. After
comparing the program information screens, I noticed that the windows
that caused the system to lock up were one that had the 'Virtualize
text/graphics' option set to yes. When I turned that off, the
windows worked. This happens with any window that gets opened with
'virtualize text/graphics' turned on. One of the main reasons for
my getting a 386SX was to have a system that could 'really' run
DesqView ,unlike my XT clone. It would especially be nice not to
get the bleed through on the screen from a program running in the
background.
I am using an EGA monitor with the Everex Micro Enhancer
graphics board and am running dos 3.3 . I have experimented using
the CMOS setup routine to set up memory in various ways:
enabling/disabling of video and bios shadow ram, 512 or 640K base ram,
etc., but still have the same problem whenever I turn on the
virtualize option.
The following is my config.sys file:
DEVICE=C:\QEMM.SYS RAM EXCLUDE=C000-CFFF EXCLUDE=
D800-DC00
buffers=40
files = 20
device = d:\mouse\mouse.sys
shell = c:\command.com c:\ /p /e:800
D800-DC00 are excluded since I believe it that my DTC hard disk
controller may be using this space. I have also excluded various
combinations, leaving only a contiguous 64K chunk for the page frame,
all with no luck.
If anyone has any tips as to what I may have set up wrong, etc.,
I would greatly appreciate it. Also, I would like to know if there
is any more documentation available about the commands (options) that
were added with rev 2.2 or 2.25 other than is available in the small
upgrade booklet that came with the software.
Thank you in advance,
Martins Gulbis
--- ConfMail V4.00
* Origin: The House of Ill Compute, Sunnyvale, CA (1:143/21)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: david nugent Area: DESQview
To: Peter Hallgarten 08 Dec 89 19:24:00
Subject: Re: DESQview and Btrieve
> I run a amateur radio bbs here the WA7MBL bbs that is written in
> pascal that uses btreive and the only problem I have found is that if
> you are running qemm as I run a 386 then you cannot allow btreive to
> use ems ram otherwise you get an error from qemm.
>
> I have tried to look for solutions for this but there seems none that
> anybody can tell me.
It agree that it's a problem in Btrieve's EMS handling. I just started
fooling with BTrieve myself (v5.0) and found precisely the same thing. When
Btrieve is active, I either prevent anything else from using EMS while it's
active (and loaded) or just disable it's EMS caching using /E (but the extra
RAM used is such a cost!).
This problem is also documented in the developer's kit. :-(
--- TosScan(q) 1.00/not quite
* Origin: Central Source - closet programmer's unite! (3:632/348)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: Peter Stern Area: DESQview
To: Allan Nelson 10 Dec 89 13:01:00
Subject: Re: Qemm 386 Problems...
AN> Re your problems with Telix, I might suggest upgrading
AN> to v3.12 which is just out. It claims to be DV aware.
AN> As for 9600 baud problems,I haven't had any yet using
AN> the HST and Telix.
I have just gotten it but the docs would indicate it has only been made
DV aware from the screen writing standard point. I brought it up as
outlined in the docs with TAME210 in front and found it was still
polling the keyboard incessantly.
Pete
--- Sirius 1.0v
* Origin: Northernmost Node..65'NORTH Fairbanks AK 907-452-1460 (1:17/38)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: Peter Stern Area: DESQview
To: Martins Gulbis 10 Dec 89 13:07:54
Subject: Re: Problem with Virt. Text/Graphics
Here is the exclude I use with my Everex Micro EGA card on an ALR 386/2
DEVICE=C:\QEMM.SYS X=A000-C7FF X=E000-E7FF X=F000-FFFF Ram
This prevents QEMM from handling ANY area marked video and any area
marked as ROM.
Pete
--- Sirius 1.0v
* Origin: Northernmost Node..65'NORTH Fairbanks AK 907-452-1460 (1:17/38)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-